Cool.

I expect I'll stop there since I am all out of ideas. ;-)

One thing you could do is to produce a version release:

git tag -a v0.1.0 -m 'version 0.1.0'
git push --tags

(If anyone wants to use this in production, they'll want to use a specific release and not just random code lifted from github.)

This will populate the "release" tab on your project.

You could also add a CHANGELOG file to track changes from now on.

Cheers!

Good idea.

The build breaks on my machine, because of the C parts. I have to
investigate further. I'd like to fix this before tagging.

Will

On Fri, Feb 14, 2014 at 2:21 PM, Daniel Lemire [email protected]:

I expect I'll stop there since I am all out of ideas. ;-)

One thing you could do is to produce a version release:

git tag -a v0.1.0 -m 'version 0.1.0'
git push --tags

(If anyone wants to use this in production, they'll want to use a specific
release and not just random code lifted from github.)

This will populate the "release" tab on your project.

You could also add a CHANGELOG file to track changes from now on.

Cheers!

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-35115599
.

Will

In particular, is it worth the 3 microseconds improvement to have a C
version? A serious question.

On Fri, Feb 14, 2014 at 3:12 PM, Will Fitzgerald
[email protected]:

Good idea.

The build breaks on my machine, because of the C parts. I have to
investigate further. I'd like to fix this before tagging.

Will

On Fri, Feb 14, 2014 at 2:21 PM, Daniel Lemire [email protected]:

I expect I'll stop there since I am all out of ideas. ;-)

One thing you could do is to produce a version release:

git tag -a v0.1.0 -m 'version 0.1.0'
git push --tags

(If anyone wants to use this in production, they'll want to use a
specific release and not just random code lifted from github.)

This will populate the "release" tab on your project.

You could also add a CHANGELOG file to track changes from now on.

Cheers!

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-35115599
.

Will

Will

Indeed. A good question. In some other tests I did, there was a more substantial difference (say 50%), but I agree that the gain is small.

But I would still be interested in knowing what breaks. Is it because cgo is not supported on your machine?

To be clearer, feel free to discard the C code. Now that I have written a blog post about it... my job is done. ;-)

This is the error:

clang: error: no such file or directory: libgcc.a

I'm sure it's my env. that's messed up. Of course, adding c increases the
complexity.

Will

On Fri, Feb 14, 2014 at 3:21 PM, Daniel Lemire [email protected]:

To be clearer, feel free to discard the C code. Now that I have written a
blog post about it... my job is done. ;-)

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-35120952
.

Will

Sure, as I said, discard the C code. (I made it easy to do...) It will remain in the logs of the project if it is ever necessary to bring it back.

I totally agree that you want to minimize complexity.